Weekly Exercises #3

library(tidyverse)     # for graphing and data cleaning
library(remotes)        # for installing package from GitHub
#remotes::install_github("llendway/gardenR") # run if package is not already installed
library(gardenR)       # for Lisa's garden data
library(lubridate)     # for date manipulation
library(ggthemes)      # for even more plotting themes
library(geofacet)      # for special faceting with US map layout
theme_set(theme_minimal())       # My favorite ggplot() theme :)

# Lisa's garden data
data("garden_harvest")

# Seeds/plants (and other garden supply) costs
data("garden_spending")

# Planting dates and locations
data("garden_planting")

# Tidy Tuesday dog breed data
breed_traits <- readr::read_csv('https://raw.githubusercontent.com/rfordatascience/tidytuesday/master/data/2022/2022-02-01/breed_traits.csv')
trait_description <- readr::read_csv('https://raw.githubusercontent.com/rfordatascience/tidytuesday/master/data/2022/2022-02-01/trait_description.csv')
breed_rank_all <- readr::read_csv('https://raw.githubusercontent.com/rfordatascience/tidytuesday/master/data/2022/2022-02-01/breed_rank.csv')

# Tidy Tuesday data for challenge problem
kids <- readr::read_csv('https://raw.githubusercontent.com/rfordatascience/tidytuesday/master/data/2020/2020-09-15/kids.csv')

Setting up on GitHub!

Before starting your assignment, you need to get yourself set up on GitHub and make sure GitHub is connected to R Studio. To do that, you should read the instruction (through the “Cloning a repo” section) and watch the video here. Then, do the following (if you get stuck on a step, don’t worry, I will help! You can always get started on the homework and we can figure out the GitHub piece later):

• Create a repository on GitHub, giving it a nice name so you know it is for the 3rd weekly exercise assignment (follow the instructions in the document/video).
  
• Copy the repo name so you can clone it to your computer. In R Studio, go to file –> New project –> Version control –> Git and follow the instructions from the document/video.
  
• Download the code from this document and save it in the repository folder/project on your computer.
  
• In R Studio, you should then see the .Rmd file in the upper right corner in the Git tab (along with the .Rproj file and probably .gitignore).
  
• Check all the boxes of the files in the Git tab and choose commit.
  
• In the commit window, write a commit message, something like “Initial upload” would be appropriate, and commit the files.
  
• Either click the green up arrow in the commit window or close the commit window and click the green up arrow in the Git tab to push your changes to GitHub.
  
• Refresh your GitHub page (online) and make sure the new documents have been pushed out.
  
• Back in R Studio, knit the .Rmd file. When you do that, you should have two (as long as you didn’t make any changes to the .Rmd file, in which case you might have three) files show up in the Git tab - an .html file and an .md file. The .md file is something we haven’t seen before and is here because I included keep_md: TRUE in the YAML heading. The .md file is a markdown (NOT R Markdown) file that is an interim step to creating the html file. They are displayed fairly nicely in GitHub, so we want to keep it and look at it there. Click the boxes next to these two files, commit changes (remember to include a commit message), and push them (green up arrow).
  
• As you work through your homework, save and commit often, push changes occasionally (maybe after you feel finished with an exercise?), and go check to see what the .md file looks like on GitHub.
  
• If you have issues, let me know! This is new to many of you and may not be intuitive at first. But, I promise, you’ll get the hang of it!

Instructions

• Put your name at the top of the document.

• For ALL graphs, you should include appropriate labels.

• Feel free to change the default theme, which I currently have set to theme_minimal().

• Use good coding practice. Read the short sections on good code with pipes and ggplot2. This is part of your grade!

• When you are finished with ALL the exercises, uncomment the options at the top so your document looks nicer. Don’t do it before then, or else you might miss some important warnings and messages.

Warm-up exercises with garden data

These exercises will reiterate what you learned in the “Expanding the data wrangling toolkit” tutorial. If you haven’t gone through the tutorial yet, you should do that first.

1. Summarize the garden_harvest data to find the total harvest weight in pounds for each vegetable and day of week (HINT: use the wday() function from lubridate). Display the results so that the vegetables are rows but the days of the week are columns.

garden_harvest %>% 
  group_by(vegetable, date, weight) %>%
  summarise(weight_lbs = weight * 0.00220462) %>% 
  select(-weight) %>% 
  mutate(day_week = wday(date, label = TRUE)) %>% 
  group_by(vegetable, day_week) %>% 
  summarise(total_harvest_lbs = sum(weight_lbs)) %>% 
  arrange(day_week) %>% 
  pivot_wider(id_cols = vegetable,
              names_from = day_week,
              values_from = total_harvest_lbs)

2. Summarize the garden_harvest data to find the total harvest in pound for each vegetable variety and then try adding the plot from the garden_planting table. This will not turn out perfectly. What is the problem? How might you fix it?

garden_harvest %>% 
  group_by(vegetable, variety, weight) %>% 
  summarise(weight_lbs = weight * 0.00220462) %>% 
  group_by(variety) %>% 
  summarise(total_harvest_lbs = sum(weight_lbs)) %>% 
  left_join(garden_planting)

It looks like there are some missing values in the plot column. Also, some of the values say things like “front” rather than a single plot letter.

3. I would like to understand how much money I “saved” by gardening, for each vegetable type. Describe how I could use the garden_harvest and garden_spending datasets, along with data from somewhere like this to answer this question. You can answer this in words, referencing various join functions. You don’t need R code but could provide some if it’s helpful.

You could join the two datasets by the matching columns of vegetable and variety. I still don’t entirely understand the difference between a left and right join and which variables are kept. To make sure all the data is available, maybe I’d do a full join. I would calculate how much you spent on each vegetable per weight in pounds harvested. This would require summarizing weight in grams to weight in pounds and then taking cost and dividing it by weight. These numbers could be directly compared to the price of produce (per pound) at a store such as Whole Foods. Whatever the difference between store price and garden price is is how much you saved by gardening the food yourself.

4. Subset the data to tomatoes. Reorder the tomato varieties from smallest to largest first harvest date. Create a barplot of total harvest in pounds for each variety, in the new order.CHALLENGE: add the date near the end of the bar. (This is probably not a super useful graph because it’s difficult to read. This is more an exercise in using some of the functions you just learned.)

garden_harvest %>% 
  filter(vegetable == "tomatoes") %>% 
  group_by(variety) %>% 
  summarise(min_date = min(date)) 

garden_harvest %>% 
  filter(vegetable == "tomatoes") %>% 
  group_by(variety, date) %>% 
  summarise(weight_lbs = weight * 0.00220462,
            total_harvest_lbs = sum(weight_lbs)) %>% 
  ungroup() %>% 
  ggplot(aes(x = total_harvest_lbs, 
             y = fct_reorder(variety, date, min, .desc = TRUE))) +
  geom_col() +
  labs(x = "",
       y = "",
       title = "Total Harvest (in lbs) for Each Tomato Variety")

5. In the garden_harvest data, create two new variables: one that makes the varieties lowercase and another that finds the length of the variety name. Arrange the data by vegetable and length of variety name (smallest to largest), with one row for each vegetable variety. HINT: use str_to_lower(), str_length(), and distinct().

garden_harvest %>% 
  mutate(lower_case_var = str_to_lower(variety),
         length_of_var = str_length(variety)) %>% 
  group_by(vegetable, variety) %>% 
  distinct(variety, .keep_all = TRUE) %>% 
  arrange(length_of_var)

6. In the garden_harvest data, find all distinct vegetable varieties that have “er” or “ar” in their name. HINT: str_detect() with an “or” statement (use the | for “or”) and distinct().

garden_harvest %>% 
  distinct(variety, .keep_all = TRUE) %>% 
  mutate(contains_er_ar = str_detect(variety, "er|ar"))

Bicycle-Use Patterns

In this activity, you’ll examine some factors that may influence the use of bicycles in a bike-renting program. The data come from Washington, DC and cover the last quarter of 2014.

A typical Capital Bikeshare station. This one is at Florida and California, next to Pleasant Pops.

One of the vans used to redistribute bicycles to different stations.

Two data tables are available:

• Trips contains records of individual rentals
• Stations gives the locations of the bike rental stations

Here is the code to read in the data. We do this a little differently than usual, which is why it is included here rather than at the top of this file. To avoid repeatedly re-reading the files, start the data import chunk with {r cache = TRUE} rather than the usual {r}.

data_site <- 
  "https://www.macalester.edu/~dshuman1/data/112/2014-Q4-Trips-History-Data.rds" 
Trips <- readRDS(gzcon(url(data_site)))
Stations<-read_csv("http://www.macalester.edu/~dshuman1/data/112/DC-Stations.csv")

NOTE: The Trips data table is a random subset of 10,000 trips from the full quarterly data. Start with this small data table to develop your analysis commands. When you have this working well, you should access the full data set of more than 600,000 events by removing -Small from the name of the data_site.

Temporal patterns

It’s natural to expect that bikes are rented more at some times of day, some days of the week, some months of the year than others. The variable sdate gives the time (including the date) that the rental started. Make the following plots and interpret them:

7. A density plot, which is a smoothed out histogram, of the events versus sdate. Use geom_density().

Trips %>% 
  ggplot(aes(x = sdate)) +
  geom_density(fill = "violet") +
  labs(x = "", y = "", title = "Density of Bike Ridership Over Time of Year") +
  theme(axis.text.y = element_blank())

8. A density plot of the events versus time of day. You can use mutate() with lubridate’s hour() and minute() functions to extract the hour of the day and minute within the hour from sdate. Hint: A minute is 1/60 of an hour, so create a variable where 3:30 is 3.5 and 3:45 is 3.75.

Trips %>% 
  mutate(hr_day = hour(sdate),
         min_day = ((minute(sdate))/60),
         hr_min = hr_day + min_day) %>% 
  ggplot(aes(x = hr_min)) +
  geom_density(fill = "violet") + 
  labs(x = "", y = "", title = "Density of Bike Ridership Over Time of Day") +
  theme(axis.text.y = element_blank())

9. A bar graph of the events versus day of the week. Put day on the y-axis.

Trips %>% 
  mutate(day_of_week = wday(sdate, label = TRUE)) %>% 
  ggplot(aes(y = fct_rev(day_of_week))) +
  geom_bar(fill = "violet") +
  labs(x = "", y = "", title = "Total Bike Ridership Over the Week")

10. Facet your graph from exercise 8. by day of the week. Is there a pattern?

Trips %>% 
  mutate(hr_day = hour(sdate),
         min_day = ((minute(sdate))/60),
         hr_min = hr_day + min_day,
         day_of_week = wday(sdate, label = TRUE)) %>% 
  ggplot(aes(x = hr_min)) +
  geom_density(fill = "violet") +
  facet_wrap(~ day_of_week) +
  labs(x = "Time of Day", y = "", title = "Density of Bike Ridership During the Day for Different Days of the Week")

Yes, it looks like on weekdays there are two peaks in bike ridership. These peaks correspond with rush hour to and from work. On the weekends, there is only one peak and that is mostly in the afternoon. Perhaps people are enjoying sleeping in on the weekends and that is why we don’t see bike ridership peak in the mornings on weekends.

The variable client describes whether the renter is a regular user (level Registered) or has not joined the bike-rental organization (Causal). The next set of exercises investigate whether these two different categories of users show different rental behavior and how client interacts with the patterns you found in the previous exercises.

11. Change the graph from exercise 10 to set the fill aesthetic for geom_density() to the client variable. You should also set alpha = .5 for transparency and color=NA to suppress the outline of the density function.

Trips %>% 
  mutate(hr_day = hour(sdate),
         min_day = ((minute(sdate))/60),
         hr_min = hr_day + min_day,
         day_of_week = wday(sdate, label = TRUE)) %>% 
  ggplot(aes(x = hr_min)) +
  geom_density(mapping = aes(fill = client), 
               alpha = 0.5, 
               color = NA) +
  facet_wrap(~ day_of_week) +
  labs(x = "",
       y = "",
       title = "Bike Ridership During Different Days of the Week, Split by Client Type")

12. Change the previous graph by adding the argument position = position_stack() to geom_density(). In your opinion, is this better or worse in terms of telling a story? What are the advantages/disadvantages of each?

Trips %>% 
  mutate(hr_day = hour(sdate),
         min_day = ((minute(sdate))/60),
         hr_min = hr_day + min_day,
         day_of_week = wday(sdate, label = TRUE)) %>% 
  ggplot(aes(x = hr_min)) +
  geom_density(mapping = aes(fill = client), 
               alpha = 0.5, 
               color = NA, 
               position = position_stack()) +
  facet_wrap(~ day_of_week) +
  labs(x = "",
       y = "",
       title = "Bike Ridership During Different Days of the Week, Split by Client Type")

I prefer the non-stack positioning. One advantage is that you can see better when casual riders and registered riders are overlapping. This is helpful if you want to know the patterns of each client. One disadvantage is that the overlapping of colors can make the graph a bit harder to read. One advantage of the stacked graphs is that it is easier to tell what proportion of riders at a certain time are casual versus registered. A disadvantage is that it’s hard to tell when the proportion of casual versus registered riders is the same.

13. In this graph, go back to using the regular density plot (without position = position_stack()). Add a new variable to the dataset called weekend which will be “weekend” if the day is Saturday or Sunday and “weekday” otherwise (HINT: use the ifelse() function and the wday() function from lubridate). Then, update the graph from the previous problem by faceting on the new weekend variable.

Trips %>% 
  mutate(hr_day = hour(sdate),
         min_day = ((minute(sdate))/60),
         hr_min = hr_day + min_day,
         day_of_week = wday(sdate),
         weekend = ifelse(day_of_week == 1 | day_of_week == 7, "weekend", "weekday")) %>% 
  ggplot(aes(x = hr_min)) +
  geom_density(mapping = aes(fill = client), 
               alpha = 0.5, 
               color = NA) +
  facet_wrap(~ weekend) +
  labs(x = "",
       y = "",
       title = "Comparing Bike Ridership Between the Week and Weekend, Split by Client Type")

14. Change the graph from the previous problem to facet on client and fill with weekday. What information does this graph tell you that the previous didn’t? Is one graph better than the other?

Trips %>% 
  mutate(hr_day = hour(sdate),
         min_day = ((minute(sdate))/60),
         hr_min = hr_day + min_day,
         day_of_week = wday(sdate),
         weekend = ifelse(day_of_week == 1 | day_of_week == 7, "weekend", "weekday")) %>% 
  ggplot(aes(x = hr_min)) +
  geom_density(mapping = aes(fill = weekend), 
               alpha = 0.5, 
               color = NA) +
  facet_wrap(~ client) +
  labs(x = "",
       y = "",
       title = "Comparing Bike Ridership Between the Client Types, Split by Week Days")

This graph is useful if your main focus in understanding how casual versus registered riders differ in their weekday versus weekend bike usage. The big takeaways from this graph is that casual riders use bikes during mid-day regardless if it is a weekday or a weekend. That would help an organization know how to best cater to the casual ridership, such as ensuring that any broken bikes are fixed by around 10 am. Personally, I prefer the graphs faceted by weekday/weekend because it is easier to see total ridership for a time of day.

Spatial patterns

15. Use the latitude and longitude variables in Stations to make a visualization of the total number of departures from each station in the Trips data. Use either color or size to show the variation in number of departures. We will improve this plot next week when we learn about maps!

Trips %>% 
  group_by(sstation) %>% 
  summarise(trips_from_station = n()) %>% 
  left_join(Stations,
            by = c("sstation" = "name")) %>% 
  ggplot(aes(x = lat, 
             y = long, 
             color = trips_from_station)) +
  geom_point() +
  labs(x = "latitude",
       y = "longitude",
       title = "total number of departures from each station")

16. Only 14.4% of the trips in our data are carried out by casual users. Create a plot that shows which area(s) have stations with a much higher percentage of departures by casual users. What patterns do you notice? (Again, we’ll improve this next week when we learn about maps).

Trips %>% 
  group_by(sstation, client) %>% 
  summarise(trips_from_station = n()) %>% 
  group_by(sstation) %>% 
  mutate(rider_percentage = trips_from_station/sum(trips_from_station)) %>%
  left_join(Stations,
            by = c("sstation" = "name")) %>% 
  ggplot(aes(x = lat, y = long, color = rider_percentage)) +
  geom_point() +
  labs(x = "latitude",
       y = "longitude",
       title = "percent of rides from different stations")

DID YOU REMEMBER TO GO BACK AND CHANGE THIS SET OF EXERCISES TO THE LARGER DATASET? IF NOT, DO THAT NOW.

Dogs!

In this section, we’ll use the data from 2022-02-01 Tidy Tuesday. If you didn’t use that data or need a little refresher on it, see the website.

17. The final product of this exercise will be a graph that has breed on the y-axis and the sum of the numeric ratings in the breed_traits dataset on the x-axis, with a dot for each rating. First, create a new dataset called breed_traits_total that has two variables – Breed and total_rating. The total_rating variable is the sum of the numeric ratings in the breed_traits dataset (we’ll use this dataset again in the next problem). Then, create the graph just described. Omit Breeds with a total_rating of 0 and order the Breeds from highest to lowest ranked. You may want to adjust the fig.height and fig.width arguments inside the code chunk options (eg. {r, fig.height=8, fig.width=4}) so you can see things more clearly - check this after you knit the file to assure it looks like what you expected.

breed_traits_total <- breed_traits %>% 
  select(-`Coat Type`, -`Coat Length`) %>% 
  group_by(Breed) %>% 
  pivot_longer(!Breed,
               names_to = "traits",
               values_to = "rating") %>% 
  group_by(Breed) %>% 
  summarise(total_rating = sum(rating)) 


breed_traits_total %>% 
  filter(total_rating > 0) %>% 
  ggplot(aes(x = total_rating, y = fct_reorder(Breed, total_rating))) +
  geom_point() +
  labs(x = "Total Rating",
       y = "",
       title = "Total Rating of Different Dog Breeds")

18. The final product of this exercise will be a graph with the top-20 dogs in total ratings (from previous problem) on the y-axis, year on the x-axis, and points colored by each breed’s ranking for that year (from the breed_rank_all dataset). The points within each breed will be connected by a line, and the breeds should be arranged from the highest median rank to lowest median rank (“highest” is actually the smallest numer, eg. 1 = best). After you’re finished, think of AT LEAST one thing you could you do to make this graph better. HINTS: 1. Start with the breed_rank_all dataset and pivot it so year is a variable. 2. Use the separate() function to get year alone, and there’s an extra argument in that function that can make it numeric. 3. For both datasets used, you’ll need to str_squish() Breed before joining.

breed_rank_all %>% 
  pivot_longer(cols = starts_with("20"),
               names_to = "year",
               values_to = "total_ranking") %>% 
  separate(year, into = c("year", "rank"), convert = TRUE) %>% 
  mutate(breed_str = str_squish(Breed)) %>% 
  inner_join(breed_traits_total %>%
               mutate(breed_str = str_squish(Breed)) %>% 
               slice_max(n = 20, order_by = total_rating),
             by = "breed_str") %>% 
  ggplot(aes(x = year, y = fct_rev(fct_reorder(breed_str, total_ranking, median)), color = total_ranking)) +
  geom_point() +
  geom_line() +
  labs(x = "",
       y = "",
       title = "Top 20 Dog Breeds by Total Ranking")

One thing that could make this graph more easily readible is if the color scale had a wider spectrum so that you could distinguish different rankings more easily.

19. Create your own! Requirements: use a join or pivot function (or both, if you’d like), a str_XXX() function, and a fct_XXX() function to create a graph using any of the dog datasets. One suggestion is to try to improve the graph you created for the Tidy Tuesday assignment. If you want an extra challenge, find a way to use the dog images in the breed_rank_all file - check out the ggimage library and this resource for putting images as labels.

breed_final <- breed_rank_all %>% 
  select(Breed, `2020 Rank`) %>% 
  inner_join(breed_traits ,
            by = "Breed") %>% 
  select(Breed, `2020 Rank`, `Openness To Strangers`) %>% 
  mutate(breed_length = str_length(Breed))

breed_final %>% 
  ggplot(aes(x =  breed_length, y = `2020 Rank`, color = `Openness To Strangers`)) +
  geom_point() +
  geom_jitter() +
  geom_smooth(method = lm)

It appears that the 2020 ranking is, contrary to popular belief, not dependent on length of the breed name and rating of openness to strangers. Who woulda thought?? :)

GitHub link

20. Below, provide a link to your GitHub page with this set of Weekly Exercises. Specifically, if the name of the file is 03_exercises.Rmd, provide a link to the 03_exercises.md file, which is the one that will be most readable on GitHub.

https://github.com/rachelpercy/2022_02_exercise_3

Challenge problem!

This problem uses the data from the Tidy Tuesday competition this week, kids. If you need to refresh your memory on the data, read about it here.

21. In this exercise, you are going to try to replicate the graph below, created by Georgios Karamanis. I’m sure you can find the exact code on GitHub somewhere, but DON’T DO THAT! You will only be graded for putting an effort into this problem. So, give it a try and see how far you can get without doing too much googling. HINT: use facet_geo(). The graphic won’t load below since it came from a location on my computer. So, you’ll have to reference the original html on the moodle page to see it.

kids %>% 
  pivot_wider(id_cols = year, 
              names_from = year,
              values_from = inf_adj) %>% 
  group_by(state, year) %>% 
  mutate(spending = inf_adj) %>% 
  ggplot(mapping = aes(x = state)) +
  geom_point(y = 1997) +
  geom_point(y = 2016) +
  geom_line() +
  facet_geo(~ state)

## Error in `stop_subscript()`:
## ! Can't subset columns that don't exist.
## x Column `year` doesn't exist.

# not sure how to finish this one
#![](kids_data_karamanis.jpeg)

DID YOU REMEMBER TO UNCOMMENT THE OPTIONS AT THE TOP?